Parts Marking System and Method

ABSTRACT

A parts marking system has memory for storing data indicative of at least one algorithm associated with at least one object material and logic configured to display the at least one algorithm to a display device and receive a user input for at least one part in response to the displayed algorithm.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 11/252,408, entitled “Parts Marking System andMethod” filed on Oct. 17, 2005 which is a continuation-in-part of U.S.patent application Ser. No. 11/818,964 filed on Oct. 15, 2005 andentitled “Parts Marking System and Method,” which claims the benefit ofU.S. Provisional Patent Application Ser. No. 60/619,489 filed on Oct.15, 2004 and entitled “Parts Marking System and Method,” each of whichare incorporated herein by reference.

BACKGROUND

Oftentimes, large entities, e.g., a government or a large corporation,manage and maintain numerous assets such as fleets of vehicles or otherheavy equipment, e.g., delivery trucks or tanks. In so managing andmaintaining, these large entities sometimes find it difficult to gatherand retain complete and reliable information for life cycle managementof property and equipment. Thus, such entities are oftentimes unable todetermine that all assets are reported, verify the existence ofinventory, substantiate the amount of reported inventory and property,or optimally use historical information for physical asset management.

In light of the foregoing, it is difficult for the large entities toachieve goals of financial reporting and accountability, e.g.,legislative goals set for government entities related to financialreporting, accountability, and life cycle management. In this regard,the entities are oftentimes unable to know the quantity, location,condition, and value of assets it owns, safeguard its assets fromphysical deterioration, theft, loss, or mismanagement, preventunnecessary storage and maintenance costs or purchase of assets alreadyon hand, and determine the full costs of programs that use these assets,e.g., government programs.

Thus, it is possible that those who manage government assets are notreceiving accurate information for making informed decisions aboutfuture funding, oversight of federal programs involving inventory, andoperational readiness.

As an example, each vehicle in a large fleet is made up of a pluralityof parts, each of which is owned and inventoried by the entity. However,information related to parts used in maintenance or parts that arealready installed on vehicles can be difficult to track.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention can be better understood with reference to the followingdrawings. The elements of the drawings are not necessarily to scalerelative to each other, emphasis instead being placed upon clearlyillustrating the principles of the disclosure. Furthermore, likereference numerals designate corresponding parts throughout the severalviews.

FIG. 1 is a block diagram illustrating a part marking system (PMS) inaccordance with an exemplary embodiment of the present disclosure.

FIG. 2 depicts exemplary implementation data, algorithms, and markingoptions for use in the PMS of FIG. 1

FIG. 3 depicts exemplary marking options for use in the PMS of FIG. 1

FIG. 4 is a block diagram illustrating a more detailed depiction of theparts marking system of FIG. 1.

FIG. 5 is a depiction of an exemplary menu graphical facilitator 101interface

(GUI) of the parts marking system of FIG. 2.

FIG. 6 is a depiction of an exemplary Add/Search GUI of the partsmarking system of FIG. 2.

FIG. 7 is a depiction of an exemplary “When to Mark Part” GUI of theparts marking system of FIG. 2.

FIG. 8 is a depiction of an exemplary “Main” GUI of the parts markingsystem of FIG. 2.

FIG. 9 is a depiction of an exemplary “Part Number Status Lists” GUI ofthe parts marking system of FIG. 2.

FIG. 10 is a depiction of an exemplary “Approval Status Update” GUI ofthe parts marking system of FIG. 2.

FIG. 11 is a depiction of an exemplary report generated by the partsmarking system of FIG. 2.

FIG. 12 is a depiction of an exemplary “Import Data” GUI of the partsmarking system of FIG. 2.

FIG. 13 is a depiction of an exemplary “General” GUI of the partsmarking system of FIG. 2.

FIG. 14 is a depiction of an exemplary “Label Analysis” GUI of the partsmarking system of FIG. 2.

FIG. 15 is a depiction of an exemplary “Information Worksheet” GUI ofthe parts marking system of FIG. 2.

FIG. 16 is a depiction of an exemplary “Label Consequences” GUI of theparts marking system of FIG. 2.

FIG. 17 is a depiction of an exemplary direct parts marking (DPM) GUI ofthe parts marking system of FIG. 2.

FIG. 18 is a depiction of an exemplary DPM algorithm GUI of the partsmarking system of FIG. 2.

FIG. 19 is a depiction of an exemplary “Enter decision” GUI of the partsmarking system of FIG. 2.

FIG. 20 is a depiction of an exemplary advantages versus limitations GUIcorresponding to laser bonding of the parts marking system of FIG. 2.

FIG. 21 is a flowchart illustrating an exemplary parts marking processperformed using the parts marking system of FIG. 2.

FIG. 22 is a flowchart illustrating exemplary architecture andfunctionality of parts marking logic of the parts marking system of FIG.2.

SUMMARY

A parts marking system in accordance with an exemplary embodiment of thepresent disclosure has memory for storing data indicative of at leastone algorithm associated with at least one object material and logicconfigured to display the at least one algorithm to a display device andreceive a user input for at least one part in response to the displayedalgorithm.

A parts marking method in accordance with an exemplary embodiment of thepresent disclosure comprises the steps of storing data indicative of atleast one algorithm associated with at least one object material anddisplaying the at least one algorithm to a display device. The methodfurther comprises receiving a user input for at least one part inresponse to the displayed algorithm.

DETAILED DESCRIPTION

Embodiments of the present disclosure generally pertain to parts markingsystems and methods. Specifically, a parts marking system (PMS) of thepresent disclosure facilitates making optimal choices regarding theapplication of an identifier on a part, hereinafter referred to as an“object identifier” (OD, and the object identifier's location on thepart. Furthermore, the system facilitates in identifying a technicallyappropriate parts marking application. Exemplary types of markingapplications include, but are not limited to labels, dot peen (DP)marking, laser bond (LB) marking, ink jet (IJ) marking, and chemicaletching (CE). Note that such list is not exhaustive and other partsmarking applications in other embodiments are possible. Note that labelrefers to any article that can be attached to an object foridentification or description purposes, e.g., a slip, a tag, a dataplate, or tape.

When determining whether a label is technically appropriate for a partand determining what type of label is technically appropriate for thepart, an exemplary PMS is used to perform a label analysis. A labelanalysis, among other things, includes identifying functions, functionalfailures, failure modes, failure effects, and consequences associatedwith each label analysis. Notably, the PMS provides a proactive analysistechnique that enables the identification of plausible failure modesrelated to marking a part with a particular label, so that appropriateaction can be identified to manage the consequences of such plausiblefailure modes.

Furthermore, when determining whether a direct parts marking (DPM)application, e.g., DP marking, LB marking, IJ marking, or CE istechnically appropriate, an exemplary PMS is used to facilitate a directparts marking (DPM) analysis. In the DPM analysis, the PMS facilitatesselecting options corresponding to particular technical limitationsassociated with available parts marking applications. Whether a partsmarking application is technically appropriate for a particular partdepends on a plurality of factors, which are described further herein.

FIG. 1 illustrates a PMS 100 in accordance with an exemplary embodimentof the present disclosure. Prior to beginning a parts marking analysisusing the PMS 100 in accordance with an exemplary embodiment, afacilitator 101 and any required team members gather implementationstrategy data related to the types of parts that are to be marked, thekinds of materials that the parts will consist of, entity restraintsrelated to the marking of parts, e.g., government regulations orcorporate guidelines, monetary factors related to the marking of parts,safety factors, whether the entity desires to track particular parts,and the like. In addition, technical limitations corresponding tospecific equipment that may be used to perform DPM techniques isgathered. Such list is not exhaustive, and other types of factors may beconsidered in other embodiments.

The PMS 100 is then configured to reflect such gathered information,which will now be described in more detail with reference to FIGS. 2-4.

After the PMS system 100 is configured according to the implementationinformation and strategies, the facilitator 101 gathers with a pluralityof team members 102-106. The facilitator 101 requests data identifying apart for analysis, which is described in more detail hereafter, and thefacilitator 101 queries the team members 102-106 in accordance with theimplementation strategy data with which the PMS system 100 wasconfigured. In this regard, the PMS system 100 provides a plurality ofoptions from which the facilitator 101 may select corresponding toparticular factors, as described herein, related to the implementationstrategy. The team members 102-106 preferably communicate datacorresponding to such requests to the facilitator 101. The number ofteam members 102-106 shown in FIG. 1 is merely an exemplary number andother numbers of team members are possible in other embodiments.

Notably, the facilitator 101 leads a parts marking analysis for anidentified part(s) by requesting particular data from the team members102-106 associated with the implementation strategies. In particular,the facilitator 101 and the team members 102-106, hereinafter referredto as the PMS team, perform a parts marking analysis so that an optimalmarking application and marking location for the identified part isachieved.

As the facilitator 101 queries the team members 102-106, the teammembers 102-106 provide information corresponding to the queries of thefacilitator 101. The facilitator 101 enters data or selects displayedoptions corresponding to the information provided from the team members102-106 into the PMS 100. Furthermore, as the facilitator 101 enters thedata into the PMS 100, the PMS 100 communicates the entered data to thevisual device 110. Such process is described in more detail throughoutthe present disclosure.

The team members 102-106 preferably comprise a group of individuals whoare knowledgeable in a particular technical area directly related to theidentified part. For example, if the part that is the subject of theanalysis pertains to the aerospace industry, the team members 102-106may comprise a system engineer, a mechanic, a depot representative, aperson responsible for technical publications, a maintenance test pilot,an instructor pilot, a crew member, and/or an original equipmentmanufacturer (OEM). Such a team comprising the members 102-106 providesa knowledge base relative to the technical area that is being analyzed.Note that the depot is a maintenance area, where particular pieces ofequipment are taken, for example, to be overhauled or repaired.

During the course of an analysis by the team members 102-106 and thefacilitator 101 using the PMS 100 of the present disclosure, there maybe required data identified during the analysis that the team members102-106 are unable to provide. In such a scenario, the PMS 100 retainsinformation corresponding to the data needed for a complete analysis, sothat such data may be sought from other sources, e.g., other experts noton the team.

Prior to initiating the parts marking analysis, the facilitator 101preferably compiles implementation information and strategies related toa plurality of assets and corresponding parts. Thus, some informationrelated to such parts is already stored in the PMS. For example, theimplementation information and strategies may identify a list of partsthat are to be marked, including part numbers, common names for theparts, nomenclature related to the parts, and the like. Additionally,the implementation information and strategies may include a list ofmarking equipment available, for example, dot peen equipment,laser-bonding equipment, chemical etching equipment, and/or ink jetequipment. The marking equipment information may further comprisetechnical limitations associated with the marking equipment available.Additionally, there may be desired factors associated with marking theselected parts. For example, an entity may desire to mark all parts thatcost more than $10,000, mark each part that may result in safetyconsequences if the part fails, mark each part that may result inenvironmental consequences if the part fails, or mark each part that theentity desires to track generally. Note that the options for inclusionin the parts marking implementation and strategies noted above aremerely exemplary. Such information and strategies may change and adaptdepending upon the use of the PMS 100.

The parts marking analysis preferably comprises numerous parts. Forexample, the analysis might comprise a label analysis for determiningthe physical aspects of the label, i.e., one-part label, two-part label,and/or other type of label known in the art and for determining if alabel is a possible marking technique for a particular part. Further,the PMS team populates an information worksheet, which includesfunctions, functional failures, failure modes, and failure effects, asdescribed hereinabove, and a label consequences analysis to determinethe consequences of a label falling off of a particular location.Furthermore, the PMS team might analyze the use of DPM for a particularpart, including separately analyzing the use of a particular DPMtechnique for each part.

FIG. 2 further illustrates how the PMS 100 uses a portion of theimplementation strategy data 2800 that is gathered by the facilitator101 or other individual(s). As described herein, the PMS 100 is to beused by the facilitator 101 and the PMS team to determine how a partwill be marked, e.g., a label or via DPM, the location on the part wherethe part will be marked, and marking instructions technicallyappropriate for each part.

Further as described herein, the implementation strategy data 2800comprises data indicating the types of DPM equipment that will be usedand the type of labels that may be used to mark particular parts.Furthermore, the implementation strategy data 2800 may comprise datadefining the technical limitations of the DPM equipment and/or thetechnical limitations of the labels. For example, some DPM techniquesmay only be able to be used on certain types of metals, e.g., aluminumor titanium, or some labels may not be applicable to a part because ofthe label's technical limitations, e.g., the label's size or the type ofadhesive that is used on a particular label.

Therefore, the PMS 100 is configured such that marking optionsidentified in the implementation strategy data 2800 are those desired bythe implementing entity, mandated by the available equipment, ornecessary for a particular part material and are available for selectionby the facilitator 101 as identified by the PMS team. Data that may beidentified in implementation information and strategies and used toconfigure the PMS system 100 will be identified throughout.

As shown in FIG. 2, the implementation strategy data 2800 is preferablyused to generate a plurality of algorithms 2801-2804. An “algorithm” inthis disclosure is a compilation of technical limitations associatedwith one or more particular parts marking techniques, and the technicallimitations may be expressed in the form of questions having selectableoptions, e.g., yes/no, I/O, or the like. The algorithms 2801-2804 aregenerated based upon the implementation information and strategies,including the type of mark, e.g., label or DPM and the type of equipmentthat will be used to adhere the mark to the part or directly mark thepart in order to determine one or more technically appropriate markingtechniques.

Therefore, an exemplary algorithm 2801 may be generated for determininga technically appropriate DPM technique for a part consisting of aparticular material, “Material A,” where a plurality of options isavailable. Note that exemplary materials might be, for example,aluminum, titanium, rubber, composite, or the like. Such list isexemplary, and other types of materials are possible in otherembodiments.

For example, the algorithm 2801 indicates that for DPM for a partconsisting of Material A, the following marking techniques areavailable, including a “Dot Peen Marking Option” 2805, an “Ink JetMarking Option” 2806, a “Chemical Etching Marking Option” 2807, and a“Laser-Bonding Marking Option” 2808. As will be described furtherherein, while each of these techniques may be available, the partsmarking analysis will further indicate, based upon any technicallimitations of the equipment or the technique, which of the markingoptions 2805-2808 is technically appropriate for the particular part.

In another example, the exemplary algorithm 2802 may be generated fordetermining a technically appropriate DPM technique for a partconsisting of a particular material, “Material B,” where only twomarking options are available. Notably, the algorithm 2802 indicatesthat the “Dot Peen Marking Option” 2805 and the “Chemical EtchingMarking Option” 2807 are technically possible for “Material B” and so isavailable for analysis. As described herein, while each of thesetechniques may be available, the parts marking analysis will furtherindicate, based upon any technical limitations of the equipment or thetechnique, which of the marking options 2805 and/or 2807 is technicallyappropriate and therefore possible for the particular part.

In another example, the exemplary algorithm 2803 may be generated fordetermining a technically appropriate DPM technique for a partconsisting either of “Material C” or “Material D.” In this regard, aparticular algorithm 2803 may be used for parts consisting of differentkinds of metals. For example, the algorithm 2803 may be used to analyzeparts consisting of titanium or consisting of aluminum. The algorithm2803 indicates two available marking options “Ink Jet” 2806 and“Chemical Etching” 2807.

In another example, the exemplary algorithm 2804 may be generated fordetermining a technically appropriate label for a part. In this regard,a particular algorithm 2804 may be used to determine whether a “One-PartLabel Marking Option” 2809 or a “two-part Label Marking Option” 2810 isdesirable. As described further herein, such an algorithm 2804 fordetermining whether a label should be used and what type of label shouldbe used may include a failure modes and effects analysis, as describedfurther herein.

FIG. 3 further describes the marking options 2805-2810. In this regard,each marking option that is available in a particular algorithm2801-2804 (FIG. 2) further comprises a plurality of technicallimitations 1161-1164 and 1188-1189. For example, the “Dot Peen MarkingOption” for a particular metal, e.g., aluminum, may only be plausible ifthe part under analysis is less than or equal to “54” on the RockwellHardness C-Scale, if the part is not used in a high pressure operatingcontext, or the part is greater than 0.020 inches thick. Thus each ofthe foregoing is a “DP Technical Limitation” 1161 corresponding to theparticular marking option, e.g., dot peen. Such technical limitationsare preferably displayed to the facilitator 101 and/or PMS team in theform of questions and/or statements, which is described in more detailwith reference to FIG. 18. Such technical limitations may be associatedwith a plurality of options for the user to select, e.g., yes/no if thelimitation is in the form of a question. Further, however, sometechnical limitations may be in the form of a statement, and thefacilitator 101, with input from the PMS team, enters data addressingsuch statement. For example, the One-Part Label Technical limitations1188 may comprise data indicative of failure modes and effects analysis.Technical limitations are described further here.

Furthermore, in each algorithm 2801-2804 there may be generallimitations related to DPM. For example, DPM may not be possible if thesurface roughness is not between 8 and 250 micro-inches, which may be ageneral technical limitation to using DPM. Thus, if the marking area cannot be prepared for DPM applications, then DPM may not be technicallyappropriate at all for the particular part and thus not available to thePMS team as a marking option.

FIG. 4 depicts a PMS 100 in accordance with an exemplary embodiment ofthe present disclosure. The exemplary PMS 100 generally comprises aprocessing unit 204, an input device 208, a display device 210, aprojection device 212, and an output device 240.

The PMS 100 further comprises parts marking logic (PML) 214 and a partsmarking database (PMD) 216. The PMD 216 comprises part data 226,information worksheet data 218, consequence data 225, label analysisdata 221, report data 220, transfer data 219, import data 281, DPM data227, and algorithm data 230. The algorithm data 230 further comprisesDPM algorithm data 231 and label algorithm data 232. Each is describedfurther herein.

In the exemplary PMS 100 shown by FIG. 4, the PMD 216 and the PML 214are implemented in software and stored in memory 202. In otherembodiments, any of the foregoing components may be implemented inhardware and/or a combination of hardware and software.

The processing unit 204 may be a digital processor or other type ofcircuitry configured to run the PML 214 and/or other software componentsof the PMS 100 by processing and executing the instructions of suchcomponents. The processing unit 204 communicates to and drives the otherelements within the PMS 100 via a local interface 206, which can includeone or more buses. Furthermore, an input device 208, for example, akeyboard, a switch, a mouse, and/or other types of interfaces, can beused to input data from a facilitator 101 of the PMS 100, and displaydevice 210 can be used to output data to the facilitator 101 (FIG. 1).

The PMS 100 may further comprise a projection device 212 that can beconnected to the local interface 206. The projection device 212 maycapture information that the facilitator 101 enters into the PMS 100 viathe input device 208. An exemplary input device 208 may include, but isnot limited to, a keyboard device, serial port, scanner, camera,microphone, or local access network connection. An exemplary displaydevice 210 may include, but is not limited to, a video display.

As noted herein, various components, such as the PML 214 and the PMD216, are shown in FIG. 2 as software stored in memory 202. Suchcomponents can be stored and transported on any computer-readable mediumfor use by or in connection with an instruction execution system,apparatus, or device, such as a computer-based system,processor-containing system, or other system that can fetch theinstructions from the instruction execution system, apparatus, or deviceand execute the instructions. In the context of this document, a“computer-readable medium” can be any means that can contain, store,communicate, propagate, or transport the program for use by or inconnection with the instruction execution system, apparatus, or device.The computer readable medium can be, for example but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system, apparatus, device, or propagation medium. Notethat the computer-readable medium could even be paper or anothersuitable medium upon which the program is printed, as the program can beelectronically captured, via for instance optical scanning of the paperor other medium, then compiled, interpreted or otherwise processed in asuitable manner if necessary, and then stored in a computer memory.

As described hereinabove, portions of the data, including the algorithmdata 230 and a portion of the part data 226, may be pre-populated basedupon the implementation information and strategies 2800 (FIG. 2). Thus,when a parts marking analysis begins, the facilitator 101 may requestinformation identifying a part for analysis, and when the facilitator101 enters such data, the PML 214 may retrieve data describing the partunder analysis from the part data 225 and display the retrieved partdata 225 to the display device 210 and the projection device 212. If thelogic 214 does not locate data corresponding to the identified part inthe part data 225, the facilitator 101 can add a new part to the partdata 226 for analysis.

If the PMS team desires to perform a label analysis on the part, thefacilitator 101 initiates a label analysis via the input device 208,which is described further herein, and the PML 214 displays labelalgorithm data 232 to the display device 210. As described hereinabove,the label algorithm data 232 may comprise a series of technicallimitations in the form of questions. Further, the algorithm data 232comprises selectable options corresponding to each of the technicallimitations and may include a failure modes and effects analysis and aconsequence evaluation, each of which is described further herein.

Thus, the facilitator 101 elicits selections corresponding to the labelalgorithm data 232 and the facilitator 101 enters such selections viathe input device 208. The PML 214 stores such responses in labelanalysis data 221 for the identified part under analysis. In thisregard, label analysis data 221 preferably comprises general datarelated to attaching a label or labels to the identified part. Forexample, the label analysis data 221 may comprise data indicative ofwhether the part is conducive to a two-part label or a one-part labeldescribed further herein. Such information is merely exemplary, andother label analysis data 221 is possible in other embodiments. Thefacilitator 101 enters label analysis data 221 via the input device 208,and the logic 214 stores such label analysis data 221 in memory 202.

The facilitator 101 elicits information worksheet data 218 from the PMSteam corresponding to the identified part. Information worksheet data218 preferably comprises data identifying functions, functionalfailures, failure modes, and failure effects corresponding to attachinga label to the identified part. Information worksheet data 218 isdescribed in more detail with reference to FIG. 15. The facilitator 101enters Information worksheet data 218 via the input device 208, and thelogic 214 stores such information worksheet data 218 in memory 202.

The facilitator 101 elicits consequence data 225 from the PMS teamcorresponding to the identified part. Consequence data 225 preferablycomprises data detailing identified consequences of a label falling offof an identified part. Consequence data 225 is described in more detailwith reference to FIG. 16. The facilitator 101 enters consequence data225 via the input device 208, and the logic 214 stores such consequencedata 225 in memory 202.

If the PMS team desires to perform a DPM analysis on the part, thefacilitator 101 initiates DPM analysis via the input device 208, whichis described further herein, and the PML 214 displays DPM algorithm data231 to the display device 210. As described hereinabove, the DPMalgorithm data 231 may comprise a series of technical limitations in theform of questions or statements. Further, the DPM algorithm data 231comprises selectable options corresponding to each of the DPM techniquetechnical limitations.

Thus, the facilitator 101 elicits selections corresponding to the DPMalgorithm data 231 and the facilitator 101 enters such selections viathe input device 208. As described hereinabove, the DPM algorithm data231 comprises questions corresponding to the materials, environment, andDPM application limitations related to the part. The PML 214 stores suchresponses in DPM data 227 for the identified part under analysis. Inthis regard, DPM data 227 preferably comprises general data related tomarking a part via one or more DPM techniques. For example, the DPM data227 may comprise data indicative of whether the part is metallic ornonmetallic, whether the part is coated, and/or what type of metal makesup the identified part. DPM data 227 is described in more detail withreference to FIG. 17. The facilitator 101 enters DPM data 226 via theinput device 208, and the logic 214 stores such DPM data 227 in the PMD216 in memory 202.

As described hereinabove, the DPM algorithm data 231 preferablycomprises specific inquiries for determining whether a part is conduciveto a particular DPM application, i.e., chemical etching, laser bonding,ink jet marking, dot peen marking, etc. Further, the DPM algorithm data231 comprises data indicative of which types of DPM techniques areidentified for use in the implementation information and strategies fora particular implementing entity. Such data is used in order toconfigure the PMS 100 specific to each implementing entity, includingoptions related to such inquiries as described hereinabove. DPMalgorithm data 231 is described in more detail with reference to FIG.18. The DPM algorithm data 231 is pre-populated in the PMS 100 prior toa parts marking analysis via the input device 208, and the logic 214stores such DPM algorithm data 231 in memory 202.

Furthermore, data related to the parts marking analysis is stored in thePMD 216, and the PML 214 generates reports 220 corresponding to the datastored in PMD 216. For example, the PML 214 may generate a reportdetailing the status of a plurality of parts, e.g., whether the partshave been analyzed, whether an analysis of the parts has been sent to avalidating authority, or whether the parts marking analysis andrecommendations have been approved by an approval authority.

FIG. 5 depicts a graphical user interface (GUI) 300 in accordance withan exemplary embodiment of the present disclosure.

The “Parts Marking” GUI 300 preferably comprises pushbuttons 301-305,and each button 301-305 displays a window, each of which is describedfurther herein, when selected by the facilitator 101 (FIG. 1).

The “Add/Search Menu” pushbutton 301 enables the facilitator 101 to adda particular part and its associated data to the PMD 216 and navigateexisting parts stored in the PMD 216. When the facilitator 101 selectsthe pushbutton 301, the PML 214 displays to the display device 210 an“Add/Search Menu” GUI 400, which is described in more detail withreference to FIG. 6.

The “Part Number Status Lists” pushbutton 302, when selected, displays aplurality of pushbuttons (not shown) that enable the facilitator 101 toretrieve lists of part numbers from the PMD 216 based on specificcriteria. Thus, the pushbutton 302, when selected, displays a “StatusLists” GUI 1900, as depicted in FIG. 9.

With reference to FIG. 9, the GUI 1900 enables a facilitator 101 to viewa plurality of status lists corresponding to a part or a plurality ofparts.

The GUI 1900 comprises pushbuttons 1901-1912. The “All Records”pushbutton 1901, when selected, displays a list of parts andcorresponding parts marking information and where such part is in anapproval process. As described further herein, the PMS 100 is used inorder to generate parts marking procedures for a plurality of parts.Such procedures for marking the parts may undergo an approval process,e.g., the team generates the information, a validation team reviews theinformation, and an approval authority approves the information. Thus,the “All Records” pushbutton 1901 may further display where each part isin the approval process.

The “Batch Numbers” pushbutton 1902 may display, when selected, a windowthat enables a facilitator 101 to display a plurality of partsassociated with a batch number. In this regard, the facilitator 101 mayenter the batch number and all the parts associated with that batchnumber are displayed, including the parts' common names and approvalstatus.

The “In Queue to Validation Team” pushbutton 1903 may display, whenselected, a window that exhibits a list of parts that are to be sent toan approval authority, e.g., a second or third tier. In this regard, ananalysis has been performed on the parts, and the parts and associatedinformation are to be provided to another tier for validation. Forexample, the list may indicate part numbers, common names andnomenclature for those parts in queue to the validation team.

The “Approval Status” pushbutton 1904 may display, when selected, awindow that exhibits a list of part numbers and their associatedapproval status when that status is chosen.

The “Type of Object Identification” pushbutton 1905 may display, whenselected, a window that exhibits a list of parts and status by theirassociated type of object identifier, when that object identification ischosen. In this regard, parts may be listed indicating DPM, DPMcandidate, or Label. Note that a DPM candidate refers to a part that iswaiting for a DPM analysis to be performed.

The “Investigate DPM” pushbutton 1906 may display, when selected, awindow that exhibits a list of parts that is waiting for a DPM analysis.In this regard, such a list comprises part numbers associated with partsthat the PMS team desires to analyze for a DPM method.

Further lists that may be generated include a list of parts by dateentered by selecting the “Facilitator by Date Entered” pushbutton 1907,a list of parts having parking lot data by selecting the “Parking Lot”pushbutton 1908, or a list of by analysis date by selecting “Analyzed byDate” pushbutton 1909. Furthermore, a facilitator 101 may generate astatus list showing a list of parts having action items by selecting the“Action Items” pushbutton 1910, or a list of parts that are not partsmarking candidates by selecting the “Not a Parts Marking Candidate”pushbutton 1911.

The GUI 1900 further comprises an “Approval Status Update; Transfer Datato Validation Team; Import Data from Validation Team” pushbutton 1912.When pushbutton 1912 is selected, a GUI 2100 is displayed as depicted inFIG. 10. The GUI 2100 enables a facilitator 101 to review data relatedto the status of a part or a batch of parts, change data related to thestatus of parts, and/or transfer data related to a part or a batch to avalidation team or an approval authority, e.g., manager or the like, sothat they can add to or comment on the data.

GUI 2100 comprises a “Choose Criteria to Populate List Below” menu 2050,a “Select New Status” menu 2051, an “Update Current Status” menu 2052,and a “Set List for Transfer” menu 2053.

The menu 2050 enables a facilitator 101 to display a part or a list ofparts in the listing window 2054. In this regard, the menu 2050comprises a text field 2101 for selecting data indicative of the currentstatus of a part or a batch of parts. Thus, for example, if thefacilitator 101 selects data indicative of a status “In Queue forValidation Team,” as described hereinabove, then the PML 214 displaysthe parts in the window 2054 from the part data 226 associated with thestatus identifier entered by the facilitator 101. Note that theexemplary window 2054 lists the parts by part number and associatedprocedure number, nomenclature, batch number, and current statusidentifier. In addition, the facilitator 101 may retrieve parts fordisplay in the window 2054 by selecting a batch number in text box 2102or by entering a procedure string in text box 2103. The text box 2104displays the total number of parts, i.e., records retrieved. Furtherpushbutton 2180, when selected, displays all part numbers associatedwith all batch numbers in the part data 226. For example, if text box2101 indicated “In Queue to Validation Team” and the text field 2102indicated batch number “3” for example, if the facilitator 101 selects“All Batches,” then the PML 214 removes the “3” limitation on the searchand displays all records from all batches that have a status of in queueto validation team.

Note that the window 2054 comprises a plurality of text boxes 2112-2115for displaying part numbers retrieved based upon criteria entered inmenu 2050. Only four text boxes 2112-2115 are shown for exemplarypurposes. However, the number of text boxes 2112-2115 displayed willdirectly reflect the number of parts retrieved based upon the criteriaentered. Furthermore, text boxes 2116-2119 display alphanumeric codesidentifying parts marking procedure, text boxes 2120-2123 displaynomenclature, text boxes 2124-2127 display batch numbers, and text boxes2128-2131 display current status identifiers corresponding to the partnumber text boxes 2112-2115, respectively.

After the facilitator 101 has selected one or more parts for display tothe window 2054, the facilitator 101 may then change the status of theparts listed. In this regard, the text boxes 2128-2131 display thecurrent status of each part listed. The facilitator 101 may select a newstatus identifier, e.g., awaiting approval, or approved, and enter thenew status in a text box 2105. The “Populate Temp Status” pushbutton,when selected, then populates “Temp Status” text boxes 2132-2135 withthe new status selected in box 2105. Note that “Delete Temp Status” maybe selected in order to delete the new status identifiers populated inthe “Temp Status” text boxes 2132-2135.

Once the facilitator 101 has selected a status identifier for the “TempStatus” text boxes associated with each part, the facilitator 101 maythen update the “Current Status” text boxes 2128-2131 by selecting the“Update Current Status with Temp Status” pushbutton 2108. When thefacilitator 101 selects the pushbutton 2108, the PML 214 changes thedata stored in the PMD 216 associated with the corresponding parts toreflect the new status identifier. In addition, the PML 214 alsodisplays the new status identifiers to the current status text boxes2128-2131.

The “Set List for Transfer” menu 2053 comprises three pushbuttons2109-2111. When the “Transfer Database” pushbutton 2109 is selected, thePML 214 generates a transfer data 219 that the PML 214 stores in memory202, as described herein. In this regard, the PML 214 retrieves datadescribing the parts associated with the part numbers displayed inwindow 2054. The PML 214 then generates the PMD 219.

The GUI 2100 may further comprise a pushbutton (not shown) that, whenselected, displays a window (not shown) for receiving recipientinformation, e.g., email address or web site address. Thus, thefacilitator 101 may then select a transfer button (not shown) based uponthe recipient information entered, and the PML 214 transmits the PMD 219to the recipient. Thus, the listed parts and associated parts markingdata making up a record in the PMD 216 may be transmitted to avalidation team and/or an approving authority for review, as describedherein.

In addition, the GUI 2100 comprises an “Import Database” pushbutton2110. When the pushbutton 2110 is selected, the PML 214 may retrieveimport data 281 and store the import data 281 in the PMD 216. The PMS100 may receive import data 281 from a validation team and/or anapproving authority, and the received import data 281 may comprisechanges to a previous transfer data 219.

Thus, the GUI 2100 further comprises a “Compare/Transfer Data”pushbutton 2111. When the pushbutton 2111 is selected, the PML 214displays a window 2300 as depicted in FIG. 5F.

The GUI 2300 displays a window 2301 populated with data related to apart number currently stored in the PMD 216. Furthermore, the GUI 2300displays a window 2302 populated with data related to the same partnumber, however, the data displayed is retrieved from the importeddatabase 219. The GUI 2300 further comprises check boxes 2304-2313corresponding at least a portion of the data contained in each of the“PMD Record” 2301 and the “Import Record 2302.” Note that the records2301 and 2302 have a plurality of text fields 2316-2328 and 2329-2341,respectively.

When a facilitator 101 desires to transfer augmented data from the“Import Record” 2302 to the “PMD Record” 2301, facilitator 101 selects acheck box 2304-2313 corresponding to that portion of the data 2316-2328and 2329-2341 that the facilitator 101 desires to transfer and selectsthe “Transfer Checked Items” pushbutton 2315. The PML 214 then replacesthe data related to the data checked in the PMD for the currentlydisplayed part number data in the “Import Record” 2302. Additionally,the facilitator 101 may select the “Check All” pushbutton to move allthe data in the “Import Record” 2302 to the “PMD Record” 2301.

The “Report Menu” pushbutton 303 enables the facilitator 101 to requestreports 220 from the PMD 216 corresponding to the PMD 216 and thealgorithmic data 230 described further herein. When the facilitator 101selects the pushbutton 303 from the GUI 300, the PML 214 displays to thedisplay device 210 a list of reports that the PML 214 can create or hasalready created. Thus, the facilitator 101 can retrieve a report anddisplay it to display device 210 or print the report to an output device240 or display such report to the display device 210 or visual device110.

An exemplary report 2400 is illustrated in FIG. 11. The report 2400depicts a label procedure report for a part named “FWD Rotary WingBlade.” The report 2400 provides the part number “118P229-71,” a commonname “FWD Blade,” a procedure number “CH88-PM-07-888A,” and a date “12May 2005.”

Additionally, the report 2400 provides a labeling procedure includingthe type of label, “2-Part Label,” and a label location, “on the damperattachment lug.” The report further exhibits a photograph or drawingthat may show the label location and the placement on the part and anyspecial installation instructions.

The “Miscellaneous Notes” pushbutton 304 may display a window (notshown) that enables the facilitator 101 to enter notes regarding aparticular part of analysis.

The “When to Mark Part” pushbutton 305 displays a GUI 2000 depicted inFIG. 7 when selected. The GUI 2000 enables a facilitator 101 and/or thePMS team to determine/view when a part is to be marked. In this regard,the GUI 2000 comprises a pull down menu 2001 that the facilitator 101can use to select a particular “When to Mark Part” opportunity and thusthe PML 214 displays the parts to be marked at that time. For example,the facilitator 101 may choose “400 HR Maintenance Cycle” and thus thePML 214 displays the parts that have been identified to be marked at the400 HR Maintenance Cycle. GUI 2000 further comprises a “Common Name”text box 2002 that displays the common name of the part, a “Part Number”text box 2003 that displays the part number of the part, and a “Type OI”text box 2004 that displays the type of object identifier, e.g., a labelor particular DPM technique, chosen by the PMS team to be used to markthe part. In addition, the GUI 2000 comprises check boxes 2005 and 2006that indicate if the part is subject to overhaul or to be at the depot,respectively. Additionally, a “Click-CM” pushbutton, when selected,displays a current maintenance schedule for the part. The GUI 2000 alsodisplays in text box 2008 that allows the facilitator 101 and the PMSteam to choose or view when the part is to be marked based on theopportunities shown in 2005, 2006, and 2007.

As mentioned hereinabove, when the facilitator 101 selects thepushbutton 301 (FIG. 5), the PML 214 displays the GUI 400 (FIG. 6) tothe display device 210. The GUI 400 comprises a text box 402 in whichthe facilitator 101 may enter data, via the input device 208, indicativeof a part number. After the facilitator 101 has entered the text intothe text box 402, the facilitator 101 selects a “Click to Add”pushbutton 414.

When the facilitator 101 selects the pushbutton 414, the PML 214 storesthe part number in the part data 226 of the PMD 216 and displays to thedisplay device 210 the “Main” GUI 500 of FIG. 8, which is described inmore detail hereafter.

Furthermore, the GUI 400 enables a facilitator 101 to search the PMD 216for existing part numbers. In this regard, the facilitator 101 maysearch existing part numbers by part number, common name, national stocknumber (NSN), or nomenclature. Thus, the GUI 400 comprises an “Enter aPart Number String” text box 404, an “Enter a Common Name String” textbox 405, an “Enter an NSN String” text box 406, and an “Enter aNomenclature String” text box 407.

When the facilitator 101 enters data into any one of the text boxes404-407 and selects a “Search” pushbutton 416, the PML 214 displays alist of part numbers associated with the entered search string, i.e.,part number, common name, NSN number, and/or nomenclature. Thefacilitator 101 can then select the part from the list of parts, andwhen the facilitator 101 selects the desired part, the PML 214 displaysthe “Main” GUI 500 (FIG. 8) exhibiting the selected part.

Additionally, the GUI 400 enables a facilitator 101 to edit and/or viewa part number. Thus, the GUI 400 comprises a “Choose a Part Number” textbox 420. When the facilitator 101 enters/chooses data into the text box420 and selects an “Edit/View” pushbutton 421, the PML 214 retrievesinformation from the PMD 216 corresponding to a part that matches thedata entered/chosen into the text box 420. The PML 214 displays theretrieved information in the “Main” GUI 500 described in more detailwith reference to FIG. 8.

In addition, the GUI 400 comprises a “Choose a Procedure to Edit” textbox 422 and corresponding “Edit/View” pushbutton 423 that, whenselected, displays the GUI 500 of FIG. 8 exhibiting the part numberassociated with the procedure number entered/chosen into the text box422 (FIG. 6). Therefore, if the facilitator 101 desires to edit aprocedure, the facilitator 101 can enter/choose the procedure numberinto text box 422, select the pushbutton 423, and the PML 214 displaysthe GUI 500 corresponding to the particular part number.

In addition, the GUI 400 comprises a “Choose a Recently Added, Searchedor Edited Part number” pull down menu 424. Therefore, the facilitator101 may select a recently added, searched or edited part number andselect the “Edit/View” pushbutton 425 to edit or view the part number orselect the “Delete History” pushbutton 426 to delete the part numbers inthe pull down menu 424 from history.

Further, the GUI 400 enables a facilitator 101 to delete a part numberfrom the PMD 216. In this regard, the facilitator 101 can enter/choose apart number into text box 427 and select the “Delete” pushbutton 428.The PML 214 then deletes the part associated with the entered/chosenpart number from the PMD 216.

FIG. 8 depicts the “Main” GUI 500. As described herein, the GUI 500 isgenerally displayed by the logic 214 when the facilitator 101 elects toretrieve information corresponding to a particular part or elects toedit an existing part stored in the PMD via the GUI 400 (FIG. 6). Inthis regard, the PML 214 retrieves desired information from the PMD 216and populates the GUI 500 with the information retrieved.

Furthermore, the “Main” GUI 500 is displayed by the logic 214 when thefacilitator 101 selects the “Click to Add” button 414 (FIG. 6). The GUI500 displays the added part number and description information and thePML 214 stores data in PMD 216 corresponding to the new part number notalready in the PMD 216. In this regard, the PML 214 displays the GUI 500to the display device 210, and the facilitator enters data into the GUI500 related to the part that the facilitator 101 desires to enter intothe PMD 216.

The GUI 500 of FIG. 8 comprises a text box 502 that the logic 214populates with a desired part number, which is entered into the GUI 400as described herein. Note that the part number, common name, and/ornomenclature displayed in text boxes 502, 504, or 506, respectively, mayalready be stored and correlated in the PMD 216. However, as describedhereinabove, the facilitator 101 may desire to enter a new part numberin GUI 400 (FIG. 6) by selecting the “Click to Add” pushbutton 414 afterentering a part number in text box 402 (FIG. 6). Furthermore, the GUI500 comprises a text box 508 for displaying or entering data thatdescribes the location of the part identified in the “Part Number” textbox 502.

In one embodiment, the GUI 500 comprises a window 510 for displayingseveral photographs and/or drawings indicative of the part identified inthe text box 502. Note that the drawing may be in any format, e.g.,portable document format (PDF), tagged image file format (TIFF), or awindows bitmap (BMP).

In this regard, the PML 214 may retrieve several photographs and/ordrawings from the PMD 216 and display the photograph or drawing in thewindow 510 along with an associated caption describing the photograph ordrawing in text box 512. Additionally, the GUI 500 comprises a “Browse”button 511. When the facilitator 101 selects the button 511, the logic214 displays data indicative of the file system (not shown) of the PMS100, and the facilitator can select from the file system a file nameindicative of a file that contains data defining a photograph or drawingof a part, which the logic 214 can display in window 510.

Furthermore, the GUI 500 may comprise an “Enlarge” pushbutton 1871, a“Select Drive” pushbutton 1872, and an “Add/Delete Label Location”pushbutton 1873. The “Enlarge” pushbutton 1871, when selected, maydisplay an enlarged version of the drawing and/or photograph in window510. The facilitator 101 and the PMS team may then be able to view inbetter detail that which is displayed in window 510.

The GUI 500 comprises a “Record Navigation” menu 515 and a “MarkAnalysis” menu 519. The “Record Navigation” menu 515 comprises a“General” pushbutton 516 and a “Main” pushbutton 518, which generallyenable a facilitator 101 to access data currently being stored in thePMD 216 (FIG. 2).

When the facilitator 101 selects the “General” pushbutton 516, the PML214 (FIG. 4) displays to the display device 210 a “General” GUI 600,which is described in more detail with reference to FIG. 13. The GUI 600(FIG. 13) provides general information about the part currently selectedin the “Part Number” text box 502 of FIG. 8.

When the facilitator 101 selects the “Main” pushbutton 518, the logic214 (FIG. 4) displays to the display device 210 the “Main” GUI 500,which is described hereinabove with reference to FIG. 8.

The “Mark Analysis” menu 519 comprises a “Label Analysis” pushbutton520, an “Information Worksheet” pushbutton 522, and a “LabelConsequences” pushbutton 524. Each button 520, 522, and 524 provides aspecific analysis functionality with respect to an object identifierthat is to be used on the part identified in the text box 502, and eachis described in more detail with reference to FIGS. 14-16.

Additionally, the GUI 500 comprises a “Direct Parts Marking” (DPM)pushbutton 526, a “Return to Search Results” pushbutton 528, a “MainMenu” pushbutton 532, and an “Edit Menu” pushbutton 530.

When the facilitator 101 selects the DPM button 526, the logic 214displays to the display device 210 the GUI 1000, which is described inmore detail with reference to FIG. 17. When the pushbutton 528 isselected, the logic 214 displays a listing of parts that may haveresulted in an earlier search as described with reference to FIG. 6. Thebutton 532 displays the “Parts Marking” GUI 300 of FIG. 5, and thebutton 530 displays GUI 400 of FIG. 6.

The GUI 500 further comprises a text box 556 for providing the status ofa record, and a button 560 that, when selected, displays the statushistory of a record. Further, the GUI 500 comprises a text box 554 fordisplaying the object identifier category of the currently displayedpart, a text box 552 for displaying a procedure number associated withthe part, and an automation button 558 for automatically formulating aprocedure number.

When the part that is currently being displayed has associatedvalidation remarks, such remarks are indicated in check box 586. In thisregard, a facilitator 101 can select “Validation Remarks” pushbutton 550to open a window comprising an editable text box (not shown). Thefacilitator 101 can enter data indicative of validation remarks in thetext box, and when the facilitator 101 returns back to the “Main” GUI500, the check box 586 exhibits a check indicating that there arevalidation remarks.

In addition, if the PMS team determines that the part currentlydisplayed is not a parts marking candidate, then the facilitator 101 canselect the push button 548, and the PML 214 displays an editable textbox (not shown) in which the facilitator 101 can enter data indicativeof reason why the part is not a parts marking candidate even though thepart meets other parts marking criteria laid out in the implementationinformation and strategies. When the facilitator 101 returns back to the“Main” GUI 500, a check box 587 exhibits a check indicating that thereare reasons indicated for why the part is not a parts marking candidate.

Furthermore, the “Facilitator Use” menu 581 comprises a “RevisionInformation” check box 589 to indicate that revisions of the informationrelated to the part exist. In this regard, the “Revision Information”pushbutton 588, when selected, displays an editable text box forentering revision information. When the facilitator 101 returns back tothe “Main” GUI 500, the check box 589 exhibits a check indicating thatthere is revision information.

As described herein, a part may be a member of a plurality of parts,wherein a batch number identifies the plurality. Data indicative of thebatch in which the part number belongs is exhibited in text box 590. Asthe approval process for parts marking descriptions for the pluralityassociated with the batch number is analyzed and reviewed, the parts canbe retrieved by searching the PMD 216 via the batch number.

The GUI 500 further comprises a check box 562 that indicates that a partis currently listed in the “Parking Lot.” Note that when a part islisted in the “Parking Lot,” such indication means that prior to makinga decision on the part's marking analysis, additional information may beneeded. Thus, the facilitator 101 can enter data describing the reasonsfor the part being in the parking lot into editable text box 534. Thus,when the facilitator 101 returns back to the “Main” GUI 500, the checkbox 562 exhibits a check indicating that there is parking lotinformation.

Further, there may be additional remarks related to the part. If so,then the GUI 500 further comprises a “Remarks” pushbutton 536 and acorresponding check box 564, which behave substantially similar to the“Parking Lot” pushbutton 534 and corresponding check box 562.

The GUI 500 may further comprise a “Record Copy” pushbutton 540, a“Spelling” pushbutton 538, and a “Master Facilitator Copy” pushbutton563. The “Spelling” pushbutton 538, when selected, checks the spellingin the displayed descriptions and other displayed text. The facilitatormay select the pushbutton 538 in order to run a spell check on theinformation provided in the GUI 500.

Further, the “Record Copy” pushbutton 540 is for providing a record copyof another part number to transport into the current working record. Inone embodiment, the pushbutton 540 displays a window from which data canbe cut and pasted into the GUI 500. In another embodiment, thepushbutton 540 automatically transports selected data into the GUI 500without the facilitator having to cut and paste the data.

“Master Facilitator Copy” pushbutton 563 is for displaying a masterrecord copy (not shown) for use by the facilitator 101. The masterrecord copy preferably is a window that shows all the informationrelated to the part including its marking information.

In addition, the “Facilitator Use” menu 581 comprises a “Date Entered”text box 544 for entering the origination date of the informationrelating to the part currently displayed in the text box 502. Furtherthe menu 581 comprises a “Date Analyzed” text box 546 for entering dataindicative of the date on which a parts marking analysis was performedfor the part number displayed in text box 502. The “Facilitator Use”menu 581 further comprises an “Action Item” pushbutton 542. Thepushbutton 542, when selected, displays a window (not shown) thatenumerates at least one action item associated with the identified part.In this regard, the action item window may exhibit data indicative ofthe part number, common name, actionee (the individual or group that isto take the action), the action to be taken, the due date, andcorresponding remarks.

Note that the data described hereinabove that is entered via the GUI 500is preferably stored in the PMD 216 as part data 226.

As described hereinabove, if the facilitator 101 selects the “General”pushbutton 516, then the PML 214 displays to the display device 210 theGUI 600 described now with reference to FIG. 13. The GUI 600, like theGUI 500, displays or receives text via text boxes, pull down menus,and/or check boxes corresponding to the “Part Number” 502, the part“Nomenclature” 504, and/or the part “Common Name” 506.

Additionally, the GUI 600 comprises a table that includes other partnumbers 608-611 that are affiliated with the part currently displayed intext box 502 and each other part number's corresponding NSNs 612-615including other cage codes. If other part numbers exist in the table,then the text box 616 provides an indication of additional part numbers,e.g., a check mark.

Additionally, the GUI 600 comprises an “Analysis Criteria” box 618. Asdescribed herein, the type of criteria that is to be considered whenanalyzing a part is dependent upon several factors, including thedesires of the implementing entity for which the part is being analyzed.In this regard, the “Analysis Criteria” box 618 can comprise a pluralityof configurable check boxes to indicate if one or more of the listedcriteria pertains to the displayed part number. For example, the box 618comprises selection boxes 619, 620, 621, and 622 and exhibit specificanalysis criteria. When box 619 is selected, this indicates that thepart costs more than $10,000, if the “safety” box 620 is checked thisindicates that the part has safety consequences, if the “environmental”box 621 is selected, this indicates that failure of the part hasenvironmental consequences, and the “tracked” box 622, if checked,indicates that the implementing entity desires to track the part numberfor a particular reason. Thus, if one or more of these boxes is check,then there exists a reason(s) for labeling the part with an objectidentifier. As described hereinabove, other analysis criteria in otherembodiments are possible depending upon the type of parts that areindicated in the implementation information and strategies for markingand any requirements that may be placed upon an implementing entity.Thus, the boxes 619-622 are configurable based upon such analysiscriteria identified.

The GUI 600 comprises an “NSN” text box 624 for displaying the NSNinformation related to the part, a “Cage Code” text box 625 fordisplaying the cage code associated with the part number, an “Parts ListFigure No.” text box 626 for displaying a figure number corresponding toa drawing associated with the part number, a source maintenancerecoverability (“SMR) Code” text box 627 for entering and/or displayingthe SMR code associated with the part number, a “Label Nomenclature”text box 628 for displaying the label nomenclature associated with thepart number, and a work unit code (“WUC”) text box 629 for enteringand/or displaying the WUC code associated with the part number. Further,the GUI 600 comprises a “Quantity of Object on Asset” text box 630 forentering and/or displaying the quantity or number of a particular partcontained on a particular asset, e.g., two rotary blades on ahelicopter. The “Latest Acquisition Cost” text box 631 may be providedfor entering and/or displaying the latest acquisition cost associatedwith the part number, and the “Latest Acquisition Date” text box 632 maybe provided for entering and/or displaying the latest acquisition dateassociated with the part number. Other information that may be providedincluding a “Field Cost” text box 633 for entering and/or displaying thefield cost for which the displayed part is bought by the end user.

The GUI 600 further provides boxes 624-633, check box 634, and textboxes 635 and 636 for entering and/or displaying information provided bythe facilitator 101 relating to the part number indicated in text box502. Such information is configurable based upon the application inwhich the PMS 100 is used. For example, the check boxes 624-634 may beused to provide additional tracking information or maintenancecharacteristics or additional maintenance and/or part management data.

Additionally, the GUI 600 comprises a “Priority” pushbutton 650, a checkbox 655, and “Add/Delete Priority” pushbutton 645. When the pushbutton650 is selected, the PML 214 displays a window comprising a list ofpriority indicators for marking of the part. Such data may include, forexample, “funding availability” priority indicator or “immediate”indicator. The facilitator 101 can add priority indicators by selectinga pushbutton (not shown). If priority data is provided for the displayedpart, the PML 214 displays an indicator in check box 655. The GUI 600further comprises a “Current Maintenance” push button 637 that, whendepressed, displays an editable text box for entered current maintenancepackage information associated with the part being analyzed. Wheninformation is entered in the editable check box, the PML 214 displaysan indicator in check box 636.

Note that each of the informational check boxes 624-633 and 635-636 arepopulated with data that is provided prior to analysis. However, some ofthe data, for example the current maintenance data in the aforedescribededitable text box, may be retrieved from the team during analysis.Further note that the analysis criteria in box 618 and the additionalinformation in text boxes 624-635 are exemplary criteria only, and othercriteria can be used in other embodiments depending upon an implementingentity's requirements.

Once the facilitator 101 has entered information corresponding to thepart number displayed in the text box 502, the PMS team performs ananalysis to determine if a label or labels are technically appropriate.In this regard, the facilitator 101 selects the “Label Analysis”pushbutton 520, and the PML 214 displays to the display device 210 a GUI700 illustrated in FIG. 14.

As described hereinabove, the “Label Analysis” screen is preferablygenerated based upon label algorithm data 232, which is obtained fromimplementation information and strategies for a particular implementingentity. For example, if it is determine that there are two types oflabels available, a one-part and a two-part, then the first question inthe “Label Analysis” GUI 700 is “Is there room for a two-part label?”

The GUI 700 comprises a selection box 702 for selecting an option thatis also provided by the label algorithm data 232. For example, theselectable option data may be an affirmative or a negative response towhether there is room on the part being analyzed for placing a two-partlabel. Thus, the PMS team answers the question of whether there is roomon the part for a two-part label, and if the PMS team determines thatthere is room for a two-part label, then the facilitator selects anaffirmative indication for the box 702. For example, the box 702 mayprovide a pull down menu when the down arrow 701 is selected. Thus, thefacilitator 101 may select a “Yes” or a “Y” from the pull down menu toindicate an affirmative response. To the contrary, the part may not besuitable for a two-part label, thus the facilitator 101 would select anegative indication, for example a “No” or an “N,” for the text box 702.

The GUI 700 further comprises a selection box 704 for selecting anaffirmative or a negative response to the question of whether there isroom on the part being analyzed for placing a one-part label. Thus, thePMS team answers the question of whether there is room on the part for aone-part label, and if the PMS team determines that there is room for aone-part label, then the facilitator selects an affirmative indicationin the box 704. For example, the box 704 may provide a pull down menuwhen the down arrow 703 is selected. Thus, the facilitator 101 mayselect a “Yes” or a “Y” from the pull down menu to indicate anaffirmative response. To the contrary, the part may not be suitable fora one-part label, in which case the facilitator 101 would enter anegative indication, for example a “No” or a “N” in the text box 704.

Notably, the queries made on the “Label Analysis” GUI 700 areconfigurable, as described hereinabove. For example, if an implementingentity that is to use the PMS 100 to perform a label analysis desiresnot to have any two-part labels, then the question corresponding to thebox 702 would not be available. Likewise, if the entity desired to useother types of labels, e.g., tape, then such a selection would beavailable. Note that the questions that are asked in the label analysisare technical limitations with respect to the use of labels. In thisregard, if the part is not big enough for a two-part label, then such aquestion describes a technical limitation to the use of the two-partlabel on the part being analyzed.

Once the PMS team determines whether a two-part label, a one-part label,and/or another type of label known in the art can be used on the part,the PML 214 automatically populates box 708 from question/answers fromboxes 702, and 704.

Further, the PMS team describes the optimal location of the labeldetermined. In this regard, the facilitator 101 enters informationdescribing the location on the part for the label type indicated in thetext box 708. Notably, the PMS team may navigate to the GUI 500described with reference to FIG. 8, by selecting the pushbutton 518, andview the photograph or drawing of the part in making the locationdetermination.

With reference to FIG. 14, the PMS team then provides informationdescribing adverse conditions that the part may be subjected to duringoperation that may affect whether or not a label is technicallyappropriate. In this regard, the GUI 700 comprises boxes 712-714including box 712 for indicating whether the label might be subject tofluid contamination, box 713 for indicating whether the label is subjectto high traffic and/or maintenance traffic, and box 714 for indicatingwhether the label is subject to adverse environmental conditions. Inaddition, the GUI 700 comprises a check box 792 for indicating whetheradverse conditions are described in more detail. In this regard, thefacilitator 101 may select the “Adverse Conditions Details” pushbutton791. If selected, the PML 214 may display a window (not shown) forentering data further describing the details, and the PML 214 may storesuch data in the PMD 216 associated with the part.

These adverse conditions questions are technical limitations to thelabel analysis. The facilitator selects options from the pull down boxes712, 713, and 714. These options and technical limitations aredetermined by the implementation information and strategies as describedhereinabove for each implementing entity. In this regard, the adversecondition questions are also configurable depending upon the type ofenvironment or external exposures that a part may endure duringoperation.

Further, the GUI 700 provides a box 718 for indicating whether thesurface area is still conducive to label application in light of theprevious analysis and exists to allow the PMS team to decide if labelanalysis should be continued. As described hereinabove, the GUI mayprovide a pull down functionality via the arrow 719. Whether the surfacearea is still conducive to label application may depend upon a number offactors that the PMS team considers in making such a determination.

Additionally, the GUI 700 comprises a technical limitation described bythe query of “Will adhesive adhere to the parts surface” and providesoptions in a pull down menu 788 for answering such a query.

Further, the GUI 700 provides a box 722 for providing an affirmative ornegative option to indicate whether there are special installationinstructions for applying the suggested label in box 708 to the partbeing analyzed. Additionally, the GUI 700 comprises a button 720, and,when selected, the logic 214 displays to display device 210 an editabletext box (not shown) in which the facilitator can enter informationdescribing the special instructions determined by the PMS team.

Further, the GUI 700 comprises a box 724 for providing an affirmative ornegative option to indicate whether the part can be marked withoutdisassembly or removal. Thus, the facilitator 101 enters an affirmativeor negative response determined by the PMS team in the box 724.Corresponding text box 726 receives data indicating the removal ordisassembly procedure/details.

The GUI 700 also comprises a box 730 for indicating affirmatively ornegatively whether the OI is accessible using a hand-held scannerwithout disassembly or removal. Thus, the facilitator 101 enters anaffirmative or negative response determined by the PMS team in the box730. Corresponding text box 728 receives data indicating the removal ordisassembly procedure/details.

The “Label Analysis” GUI 700 embodies exemplary label algorithm data232. In this regard, the questions/statements and options provided torespond to the exemplary questions/statements make up an exemplary labelalgorithm. Other questions/statements in other embodiments of a “LabelAnalysis” GUI 700 can be used with other options, and such algorithmscan be configured based upon the implementation information andstrategies as described herein.

The PMS 100 stores data indicative of the selected options and otherdata entered in the “Label Analysis” GUI 700 in the label analysis data221 of the PMD 216.

Once the PMS team performs the basic label analysis using GUI 700, thefacilitator continues the analysis by selecting the “InformationWorksheet” pushbutton 522. When the pushbutton 522 is selected, thelogic 214 displays the GUI 800 depicted in FIG. 15 to the display device210.

The GUI 800 enables the PMS team to perform an information worksheetanalysis via the display device 210 and the visual device 110. In thisregard, the PMS team begins by identifying a variety of functions,functional failures, failure modes, and failure effects related to theplacing of a label on a part or such functions, functional failures,failure modes, and failure effects may be identified prior to the PMSteam gathering, and the PMD 216 may be populated with function,functional failure, failure mode, and failure effect data. In thisregard, the pre-populated identified functions, functional failures,failure modes, and failure effects may be technical limitationsassociated with an algorithm, and such functions and functional failuresmay be stored in the information worksheet data 218 (FIG. 4).

Such function data is entered or displayed into text box 811. Whenadding a function, the facilitator 101 selects the “Add” pushbutton 801.As the facilitator 101 enters additional functions or scrolls throughpre-populated functions, the PML 214 increments a counter in text box837.

Exemplary functions that may be identified by the PMS team include, forexample, to safely and permanently display human and machine-readablepart information so that it can be identified and traced, to avoiddamage to the part and/or the vehicle in which the part is installed,and to avoid introducing any additional failure modes to the system inwhich the part is installed. Note that such functions may vary fordifferent applications of the PMS 100.

Once the PMS team has reviewed pre-populated functions and/or added newfunctions associated with the label under analysis, the PMS teamidentifies “Functional Failures” associated with each pre-populatedfunction and/or added function. As functional failures are identified,the facilitator 101 enters such functional failure data by selecting an“Add” pushbutton 802 and entering data into the text box 812 describingthe functional failure. A counter in text box 827 indicates the numberassociated with the displayed functional failure in text box 812.

Exemplary functional failures associated with an identified function mayinclude the label falls off, the label is humanly illegible, or thelabel is not machine-readable. Note that such functional failures mayvary for different implementing entities of the PMS 100.

Once the PMS team has identified functional failures associated with thelabel under analysis, the PMS team identifies “Failure Modes” associatedwith the identified functional failures. The facilitator 101 enters suchfailure mode data by selecting an “Add” pushbutton 803 and entering datadescribing the failure mode in text box 813.

Once the PMS team has identified failure modes, the PMS team identifies“Failure Effects” associated with each failure mode identified. Thefacilitator 101 enters such failure effects into the text box 814associated with each failure mode. The described compilation of failuremodes and failure effects is hereinafter referred to as a “FMEA.”

Based on the FMEA, if the PMS team desires to continue the labelanalysis, the GUI 800 comprises a box 806 for indicating an affirmativeor negative response as to whether to still continue the analysis.Further, the GUI 800 comprises a box 804 for indicating an affirmativeor negative response as to whether the label determined in text box 708(FIG. 14) is recommended in light of the information provided in theFMEA.

Note that the “Record Navigation” menu 515 and the “Mark Analysis” menu519 behave in substantially the same manner as described hereinabove.

Furthermore, the GUI 800 comprises a “Facilitator Use” box 599. The box599 comprises a “Spell Check” pushbutton 561 that, when selected, checksthe spelling in the text boxes in the GUI 800. The box 599 furthercomprises a “Totals” pushbutton 562 that when depressed displays a textbox (not shown) that details the total number of functions, functionalfailures, failure modes, and failure effects contained in theinformation worksheet performed in the GUI 800, when selected. The“Copy” pushbutton 563 displays a copy of the current window so that thefacilitator 101 can copy data from one window to the working GUI 800.Further, the “Copy” pushbutton 563 is for providing a record copy ofanother part number to transport into the current working record. In oneembodiment, the pushbutton 563 displays a window from which data can becut and pasted into the GUI 800. In another embodiment, the pushbutton563 automatically transports selected data into the GUI 800 without thefacilitator having to cut and paste the data.

Finally, the box 599 comprises a “Renumber” pushbutton 564 thatrenumbers functions, functional failure, failure modes, and failureeffects when selected.

The PML 214 stores the FMEA data and any other data entered in the“Information Worksheet” GUI 800 in the information worksheet data 218(FIG. 4).

Once the Information Worksheet GUI 800 is completed by the PMS team, thefacilitator 101 may select the “Label Consequences” button 524, and thelogic 214 displays the GUI 900 described in more detail hereafter withreference to FIG. 16.

The GUI 900 further exhibits a plurality of questions indicative oftechnical limitations associated with the consequences of a particularlabel falling off of its location identified in text box 710 (FIG. 14),as described hereinabove. In this regard, the GUI 900 comprises textboxes for entering data and selection boxes for selecting optionscorresponding to a plurality of queries aimed at gathering informationcorresponding to the consequences of a label falling off which allowsthe PMS team to select a label as a marking option.

The GUI 900 comprises a text box 902 for entering data describing wherea label conducive to detachment might fall off. Thus, the facilitator101 requests information from the PMS team corresponding to where alabel(s) would fall off, and the facilitator 101 enters such informationin text box 902.

The PMS team further analyzes the consequences if the label falls offvia the GUI 900 by entering data in boxes 903-907. Furthermore,pushbuttons 910-914 may be selected so that the facilitator 101 canenter additional data regarding each box 903-907.

In this regard, the GUI 900 comprises text box 903 for providing anaffirmative or negative response as to whether, if the label beinganalyzed falls off, if such falling off might have adverse effects onoperational safety. If the PMS team determines that there are or are notsafety consequences, the GUI 900 further provides a pushbutton 910, andwhen the button 910 is selected, the logic 214 displays an editable textbox (not shown) for entering detailed information corresponding tosafety consequences information identified by the PMS team.

The GUI 900 comprises text box 904 for providing an affirmative ornegative response as to whether, if the label being analyzed falls off,such falling off might cause a breach of an environmental standard orregulation. If the PMS team determines affirmatively/negatively thatthere are environmental consequences, the GUI 900 further provides apushbutton 911, and when the button 911 is selected, the logic 214displays an editable text box (not shown) for entering detailedinformation corresponding to the environmental consequences informationidentified by the PMS team.

The GUI 900 comprises text box 905 for providing an affirmative ornegative response as to whether, if the label being analyzed falls off,such falling off might cause an adverse effect on operationalcapability. If the PMS team determines affirmatively/negatively thatthere are operational consequences, the GUI 900 further provides apushbutton 912, and when the button 912 is selected, the logic 214displays an editable text box (not shown) for entering detailedinformation corresponding to the operational consequences informationidentified by the PMS team.

The GUI 900 comprises text box 906 for providing an affirmative ornegative response as to whether, if the label being analyzed falls off,such falling off might cause equipment damage. If the PMS teamdetermines affirmatively/negatively that there may be equipment damageconsequences, the GUI 900 further provides a pushbutton 913, and whenthe button 913 is selected, the logic 214 displays an editable text box(not shown) for entering detailed information corresponding to theequipment damage information identified by the PMS team.

The GUI 900 comprises text box 907 for providing an affirmative ornegative response as to whether, if the label being analyzed falls off,is the level of risk associated with such falling acceptable. If the PMSteam determines affirmatively/negatively that the level risk associatedwith the label falling off is acceptable, the GUI 900 further provides apushbutton 914, and when the button 914 is selected, the logic 214displays an editable text box (not shown) for entering detailedinformation corresponding to details regarding the level of riskassociated with the label(s) falling off identified by the PMS team.

In light of the information provided regarding the consequences of thelabel falling off, the PMS team then determines whether the label beinganalyzed is recommended. If the team determines that the label isrecommended, the GUI 900 comprises a box 908 for entering an affirmativeindication, i.e., a “Yes” or a “Y,” that indicates that the label isrecommended. Otherwise, the facilitator 101 can enter data indicatingthat the team does not recommend the analyzed label, i.e., a “No” or a“N.” If a negative entry is made in text box 908, the PML 214 displays adialog box (not shown) that asks whether to continue to the DPManalysis, as described with respect to FIG. 17.

The GUI 900 further comprises a “First Iteration” selection box 961 forselecting whether the recommendation made in box 908 is a result of afirst iteration of the algorithm exhibited by GUI 700 (FIG. 14), GUI 800(FIG. 15), and GUI 900 (FIG. 16). If it is not the first iteration, thenthe facilitator 101 selects a negative indication form the pull down box961. In one embodiment, the facilitator 101 selects the pushbutton 962,and the PML 214 displays an editable text (not shown) for entering datadescribing the first iteration so that an audit trail of decisions canbe maintained.

As described herein, DPM is distinguishable from marking via a label. Inthis regard, DPM refers to placing part information directly on thepart. Thus, the PMS team determines whether the part is conducive to DPMby using the GUI 1000 depicted in FIG. 17 and the GUI 1100 depicted inFIG. 18.

Furthermore, GUI 1000 and GUI 1100 embody an exemplary algorithm, e.g.,algorithms 2801-2803 (FIG. 2), which will be indicated further herein.

The exemplary GUI 1000 comprises a plurality of questions correspondingto an algorithm for deciding upon a DPM technique. In this regard, theGUI 1000 comprises a text box 1002 for indicating whether the partcomposition is a metal or a nonmetal. Exemplary metals include, forexample, titanium or aluminum. Exemplary nonmetals include, for example,rubber, plastic, or composite materials. As described hereinabove,different materials will have different algorithms associated with them.Thus, the GUI 1000 will change depending upon the type of part that isbeing analyzed.

In this regard, the text box 1002 may comprise a pull down menu 1001that lists a plurality of options for the facilitator 101 and the PMSteam when selecting data in response to this question. The menu maycomprise the different available selections, e.g., metal or nonmetal.Note that the questions related to DPM may vary depending upon theparticular application of the GUI 1000. Furthermore, the PML 214determines the algorithm that is employed in GUI 1100 based upon theselections made on GUI 1000 (FIG. 17). In this regard, if it is a metaland that metal is further identified as “aluminum”, then an algorithmcomprising marking options corresponding to techniques that are to beused for marking aluminum is displayed when the algorithm is run byselecting a “Run Algorithm” pushbutton 1012, described further herein.

The GUI 1000 further comprises a text box 1004 for indicating whetherthe surface of the part is painted. In this regard, the text box 1004may comprise a pull down menu (not shown) actuated by selecting thearrow 1003. The menu may comprise the different available selections,e.g., painted/not painted or true/false. Further, the facilitator mayenter an affirmative or negative response, for example, if the surfaceis painted, the facilitator 101 enters a “Yes” or a “Y” in the text box1004 by entering text into the box 1004 or selecting an affirmativeindication from a pull down menu displayed by selecting the arrow 1003.Again, the algorithm employed to determine whether the part can bemarked using DPM and the marking options available for marking the partmay aid in defining the algorithm that is employed in GUI 1100,described further herein.

The GUI 1000 further comprises a text box 1006 for indicating whetherthe surface can be prepared for DPM application. In this regard, thetext box 1006 may comprise a pull down menu (not shown) actuated byselecting the arrow 1005. The menu may comprise the different availableselections, e.g., “yes” or “no.” Note that if the surface cannot beprepared for DPM, and the facilitator 101 answers “no” in box 1006 viathe pull down menu 1005, then the PML 214 indicates in text box 1016that DPM is not possible.

The GUI 1000 further comprises a text box 1008 for indicating the typeof metal that the part is made of. In this regard, the text box 1008 maycomprise a pull down menu (not shown) actuated by selecting the arrow1007. The menu may comprise the different available selections, e.g.,aluminum, steel, bronze, and/or brass. Note that the pull downselections, e.g., aluminum, steel, bronze, etc., can be populateddepending upon the type of application for which the PMS 100 is beingused for a specific implementing entity. Furthermore, the PML logic 214determines the algorithm that is employed in GUI 1100 based upon theselection made in text box 1008. In this regard, if the part isaluminum, then an algorithm comprises DPM marking options correspondingto techniques that are technically possible for marking aluminum and isdisplayed when the algorithm is run by selecting a “Run Algorithm”pushbutton 1012, described further herein. Furthermore, the answers intext boxes 1002 and 1008 determine the “Metal Group” 1010 in which thepart is a member. In this regard, there may be several metals, e.g.,aluminum and steel, which belong to the same metal group in that thesame algorithm can be used to determine the type of DPM that can beemployed to mark the part.

When the facilitator 101 selects the button 1012, the PML 214 displays aGUI 1100 described in more detail with reference to FIG. 18. The GUI1100 aids the PMS team in deciding which type of DPM is recommended inregard to the part being analyzed.

Once the algorithm is run, the GUI 1000 comprises a “DPM AnalysisResults” box 1015 that indicates whether DPM is possible and what typesof DPM are possible and not possible for the part being analyzed.

In this regard, the box 1015 indicates in a text box 1016 an affirmativeor a negative indication of whether it is possible to use DPM. If DPM ispossible at all, the box 1015 further comprises boxes 1018-1021 thatindicate which types of DPM are possible, and boxes 1022-1025 thatindicate which types of DPM are not possible.

Further, the GUI 1000 comprises a text box 1088 or a pull down menu (notshown) that allows the facilitator 101 to choose which DPM technique isrecommended by the PMS team.

As indicated hereinabove, when the facilitator 101 selects the button1012, the PML 214 displays GUI 1100 of FIG. 18. The PML 214 selects oneof a plurality of algorithms that are coded into PML 214 prior toanalysis and are based on the specific implementation strategies for aparticular implementing entity for display in GUI 1100 based upon theanswers to the queries in GUI 1000 (FIG. 17).

The GUI 1100 enables the PMS team to determine which types of DPM aretechnically appropriate, if any. In this regard, the GUI 1100 comprisesa text box 1102 for displaying the metal identified in box 1010 (FIG.17) and a text box 1104 for displaying the part number associated withthe part currently being analyzed. Furthermore, the GUI 1100 provides abox 1106 for indicating which step the PMS team is currently on as itgoes through each step in the algorithm depicted in GUI 1100.

As noted herein, the algorithm displayed in GUI 1100 depends uponanswers to questions in GUI 1000. In this regard, the algorithm in GUI1100 comprises four decision areas 1196-1200. As the facilitator 101enters data indicative to options related to each of the part markingtechniques, the PML logic 214 determines, based upon the data entered,whether the marking technique related to the data being entered ispossible or not possible. The PML 214 then automatically moves thefacilitator 101 on the GUI from one marking technique area 1196-1200 toanother.

In decision area 1200, the PMS team analyzes whether the part generallycan be marked using a DPM method by displaying questions (not shown)related to general technical DPM limitations. For example, if the parthas a surface on which a DPM can be placed or if the surface thicknessis adequate for placing a DPM. Note that these questions areconfigurable based upon the implementing entity for which the particularPMS 100 is designed. For example, aerospace research may disallow DPMfor surfaces of a particular thickness or made of a particular type ofmetal. If the facilitator 101 enters data, based upon input from the PMSteam, that indicates that DPM is possible, then the PML 214automatically controls the analysis flow by highlighting and/ordisabling selected decision areas based upon the options selected by thefacilitator 101 corresponding to the technical limitations of each DPMtechnique as described further herein. In this regard, as describedherein, the algorithm displayed comprises the decision areas 1196-1199corresponding to DPM techniques determined to be technically appropriatefor the material displayed in text box 1102.

Note that, based upon the answers to the questions in decision area1200, none or all of the decision areas 1196-1199 may be made editableby the PML 214. Likewise, based upon the answers to the questions indecision areas 1196-1199, one or more of the decision areas 1196-1199may be made editable by the PML 214.

In one embodiment, if each general technical DPM limitation in decisionarea 1200 is answered affirmatively, then the PML 214 enables each ofthe decision areas 1196-1199. However, in other embodiments of thealgorithm, other combinations of enabled/disabled decision areas1196-1199 are possible and are dependent upon the affirmative/negativeselected options in decision areas 1196-1199.

If each decision area 1196-1199 is technically appropriate, the PML 214enables all decision areas 1196-1199 and automatically moves anindicator (not shown) to the dot peen technical limitations 1161. Thus,the facilitator 101 and the PMS team may then provideaffirmative/negative responses corresponding to the dot peen technicallimitations 1161 of the decision area 1196. If during analysis of thedot peen technical limitations 1161 the facilitator 101 enters anegative response, then the PML 214 automatically moves the indicator tothe ink jet technical limitations 1162 of the decision area 1197. If theanswers to such technical limitations indicate that dot peen can not beperformed, then the PML 214 (FIG. 4) places a “No” in text box 1144. Ifthe answers to such technical limitations indicate that dot peen can beperformed, then the PML 214 (FIG. 4) places a “Yes” in text box 1130.,

Thus, as indicated herein above, after it is determined whether or notdot peen is possible, the PML 214 automatically moves the indicator tothe ink jet technical limitations 1162 of the decision area 1197. Ifduring analysis of the ink jet technical limitations 1162 thefacilitator 101 enters a negative response, then the PML 214automatically moves the indicator to the laser bond technicallimitations 1163 of the decision area 1198. If the answers to suchtechnical limitations indicate that ink jet can not be performed, thenthe PML 214 (FIG. 4) places a “No” in text box 1145. If the answers tosuch technical limitations indicate that ink jet can be performed, thenthe PML 214 (FIG. 4) places a “Yes” in text box 1140.,

Thus, as indicated herein above, after it is determined whether or notink jet is possible, the PML 214 automatically moves the indicator tothe laser bond technical limitations 1163 of the decision area 1198. Ifduring analysis of the laser bond technical limitations 1163 thefacilitator 101 enters a negative response, then the PML 214automatically moves the indicator to the chemical etching limitations1164 of the decision area 1199. If the answers to such technicallimitations indicate that laser bond can not be performed, then the PML214 (FIG. 4) places a “No” in text box 1160. If the answers to suchtechnical limitations indicate that laser bond can be performed, thenthe PML 214 (FIG. 4) places a “Yes” in text box 1162.

Thus, as indicated herein above, after it is determined whether or notlaser bond is possible, the PML 214 automatically moves the indicator tothe chemical etch technical limitations 1164 of the decision area 1199.If during analysis of the chemical etch technical limitations 1164 thefacilitator 101 enters a negative response, then the PML 214 places a“No” in the text box 1146 and the algorithm terminates. If the answersto such technical limitations indicate that chemical etching can beperformed, then the PML 214 (FIG. 4) places a “Yes” in text box 1148 andthe algorithm terminates

Note that, the decision areas 1196-1199 are arranged in successionwithin the algorithm so that each decision area 1196-1199 isenabled/disabled as a result of the affirmative/negative answers to thegeneral technical limitations or preceding technical limitations1161-1163. In this regard, the PML 214 automatically moves the indicatorfrom the preceding decision area 1200 or 1196-1198 to the next decisionarea 1196-1199. However, in other embodiments, the decision areas may beenabled/disabled and the indicator may be automatically movedindependent of the affirmative/negative answers to the precedingtechnical limitations 1161-1163.

In yet another embodiment, if in decision area 1200, based upon optionsselected in the general technical DPM limitations 1200, the PML 214determines that chemical etching, for example, is the only technicallyappropriate DPM technique, the PML 214 may only enable chemical etchingdecision area 1199. Thereafter, chemical etch decision area 1199 behavesas described herein above.

As noted herein above, if the questions answered in the generaltechnical DPM limitations in decision area 1200 indicate that more thanjust chemical etching decision area 1198 is technically appropriate,those applicable decision areas 1196, 1197, and 1199 are enabled by thePML 214.

Note that, the DPM techniques illustrated in GUI 1100 are for exemplarypurposes and varying combinations of those identified DPM techniques ordifferent DPM techniques may be used in other embodiments. Further notethat, four DPM techniques are shown in the algorithm in GUI 1100 forexemplary purposes. However, other quantities of DPM techniques in otherembodiments are possible.

GUI 1100 further comprises a “Facilitator Use” menu 1121. The menu 1121provides text boxes 1167 and 1169 for entering additional informationrelated to the part being analyzed. In this regard, if there isadditional information needed in order to make a determination as to thelabel algorithm, the facilitator 101 selects the “Parking Lot”pushbutton 1167, and the PML 214 displays an editable text box (notshown) for entering information corresponding to the additionalinformation needed for the analysis. The PML 214 then enters anindication in the “Parking Lot” box 1166, e.g. a check mark, indicatingthat additional information is needed. Further, the GUI 1100 providesthe “DPM Remarks” check boxes 1168, and the PML 214 enters an indicationin the check box 1168 that there are DPM remarks associated with thepart being analyzed if the facilitator 101 enters data by selecting the“DPM Remarks” pushbutton 1169. Thus, when the facilitator 101 selectsthe “DPM Remarks” pushbutton 1169, the logic 214 displays an editabletext box (not shown) for entering information corresponding to theremarks related to the analysis.

Further, the “Facilitator Use” menu 1121 comprises a “Start Over” button1170. Thus, if the facilitator 101 and/or the PMS team determine thatthe algorithm being performed needs to be started over, the logic 214resets the GUI 1100 when the facilitator selects button 1170. The menu1121 also comprises a “Return to DPM” button 1172, and if thefacilitator 101 determines that the GUI 1000 (FIG. 17) is needed duringthe analysis, the PML 214 displays the GUI 1000 when the facilitator 101selects the button 1172.

With respect to FIG. 17, once the PMS team has completed running thealgorithm in FIG. 18, the facilitator 101 may select the “EnterDecision” button 1014. When button 1014 is selected, the logic 214displays the “Enter Decision for PN” GUI 1200 depicted in FIG. 19.

GUI 1200 illustrated in FIG. 19 comprises a text box 1202 for displayingthe suggested order of the parts marking as a result of the DPMalgorithm. Such suggested order is predetermined during theimplementation information and strategies development, therefore, thetext field 1202 is pre-populated. As an example, text field 1202 mightexhibit “ink jet, dot peen, chemical etch,” and this order may have beendetermined based upon cost or other factors.

Further, the GUI 1200 comprises text box 1204 for displaying the currentpart number and a text box 1205 for displaying the current part commonname. Further, the GUI 1200 comprises a “DPM Techniques Advantages andLimitations” menu 1208 that shows each of the DPM techniques included inPML 214. The menu comprises pushbuttons 1210-1213 that, when selected,displays the advantages and limitations associated with each DPMtechnique. Menu 1208 provides a laser bonding button 1210, ink jetbutton 1211, chemical etching button 1212, and dot peen button 1213, andif the facilitator 101 selects, for example, the laser bond button 1210,the PML 214 displays GUI 1300 of FIG. 20 for PMS team referencepurposes. The GUI 1200 further comprises a text box 1288 for enteringdata indicative of a technically appropriate DPM method chosen by thePMS team for marking the part as a result of the algorithm.

GUI 1300 provides a summary of the advantages and limitationscorresponding to laser bond DPM. In this regard, the GUI 1300 maycomprise a box 1302 enumerating the advantages of laser bond DPM, whichmay include that laser bond parts marking is resistant to high heat, isunaffected by salt, fog, and/or spray, exhibits the best resolution, isconsistent, and is a non-contact application. On the other hand, the GUI1300 may comprise a box 1304 enumerating the limitations of laser bondparts marking, which may include that the laser bond parts marking islimited to the work enclosure, it cannot be used to mark on a paintedsurface, and it is time intensive. GUI 1300 in FIG. 13 displaysadvantages and limitations specific to laser bonding, however, othertechniques will be correlated with other Advantages/Limitations fordisplay in GUI 1300 in other embodiments.

FIG. 21 is a flowchart illustrating an exemplary parts marking processof the present disclosure.

The facilitator 101 and/or the PMS team identify a part for analysis instep 1402. Preferably, information relating to the part identified isgathered prior to any parts marking analysis. For example, thefacilitator 101 may collect information including a drawing and/or aphotograph or a specification sheet corresponding to the part.Furthermore, as described herein, data relating to a part may bepre-populated prior to the analysis in the “General” GUI 600 depicted inFIG. 13.

The PMS team then determines whether a label analysis is desired in step1404. If a label analysis is not desired in step 1404, then the PMS teamdetermines in step 1414 whether a DPM analysis is desired.

If a label analysis is desired, then the PMS team performs a labelalgorithm in step 1406. In this regard, the PMS team determines whethera one-part or two-part label, for example, can be used on the part.Further, the PMS team determines a location for the label, adverseconditions that may affect the label, and other installationinstructions. Note that such technical limitations corresponding to alabel algorithm are configurable and may change depending upon theimplementation strategy and the implementing entity.

The PMS team then performs a function, functional failure, failure modeand failure effect analysis related to the application of the label onthe identified part in step 1408. The PMS team then determinesconsequences related to the label falling off in step 1410.

Based upon the information obtained in steps 1406, 1408, and 1410, thePMS team provides a recommendation on the type of label to use in step1412.

If a label is not desired in step 1404 or in addition to recommending alabel in step 1412, the PMS team then determines whether direct partsmarking (DPM) is desirable for the part under analysis in step 1414. IfDPM is not desirable, then the analysis ends. However, if DPM isdesired, the PMS team analyzes each DPM technique that is pre-populatedin the PMS 100 and whether one of the pre-populated DPM techniques canbe used on the part in step 1416.

After the PMS team determines the types of DPM that are technicallyappropriate for use on the part, the PMS team then determines arecommendation of a DPM technique based upon the PMS team analysis and aprioritized list pre-populated of DPM techniques that may be used tomark the part in step 1418.

FIG. 22 is a flowchart depicting architecture and functionality ofexemplary PML 214 (FIG. 2) of the present disclosure.

The PML 214 configures parts marking options based upon implementationstrategies in step 1504. For example, an implementing entity mayidentify that it is technically appropriate to use labels and specificDPM techniques to mark parts. Such information is used to configure thePMS 100 such that options are made available to the PMS team duringanalysis to reflect the implementation strategies.

The PML 214 then stores data indicative of a plurality of parts formarking in step 1506. The PML 214 then receives data indicative of partsmarking options corresponding to at least one of the parts in step 1508.

The PML 214 then stores data indicative of the determined best partsmarking alternative and receives data indicative of a marking procedurecorresponding to the selected alternative in step 1510. The PML 214generates at least one report associated with the best parts markingalternative and marking procedure corresponding to the alternative instep 1512.

1. A parts marking system for determining a type of direct parts marking(DPM) to be used for a particular part, comprising: memory for storingdata indicative of a plurality of materials out of which the part can bemade and storing in memory for each material a plurality DPM techniquesand a plurality of technical limitations associated with the DPMtechnique, the technical limitations including data for determiningwhether each DPM technique can be used based upon each material; logicconfigured to receive data, via a graphical user interface (GUI),identifying a part and a material out of which the part is made, thelogic further configured to display, via the GUI, data identifying atleast one of the DPM techniques and the technical limitations associatedwith the DPM technique, each limitation displayed in the form of aquestion, the DPM technique and the technical limitations displayedbased upon the data identifying the part and the material out of whichthe part is made.
 2. The parts marking system of claim 1, wherein thelogic is further configured to display one or more general technicallimitations relating to DPM techniques in the form of questions.
 3. Theparts marking system of claim 1, wherein the logic is further configuredto determine, based upon one or more inputs in response to the questionscorresponding to the one or more general technical limitations, that DPMis not possible for the identified part and characteristics of thematerial.
 4. The parts marking system of claim 2, wherein the logic isfurther configured to determine, based upon one or more inputs inresponse to the questions corresponding to the one or more generaltechnical limitations, that DPM is possible for the identified part andthe identified material.
 5. The parts marking system of claim 1, whereinthe logic is further configured to display one or more specifictechnical limitations relating to a particular DPM technique in the formof questions.
 6. The parts marking system of claim 5, wherein the logicis further configured to determine, based upon one or more inputs inresponse to the questions, whether the particular DPM technique ispossible for the identified part and the identified material.
 7. Theparts marking system of claim 5, wherein the specific technicallimitations and the corresponding questions are related to a dot peenDPM technique.
 8. The parts marking system of claim 7, wherein the logicis further configured to determine, based upon one or more inputs inresponse to the questions, whether the dot peen DPM technique ispossible.
 9. The parts marking system of claim 5, wherein the specifictechnical limitations and the corresponding questions are related to anink jet DPM technique.
 10. The parts marking system of claim 9, whereinthe logic is further configured to determine, based upon one or moreinputs in response to the questions, whether the ink jet DPM techniqueis possible.
 11. The parts marking system of claim 5, wherein thespecific technical limitations and the corresponding questions arerelated to a chemical etch DPM technique.
 12. The parts marking systemof claim 11, wherein the logic is further configured to determine, basedupon one or more inputs in response to the questions, whether thechemical etch DPM technique is possible.
 13. The parts marking system ofclaim 5, wherein the specific technical limitations and thecorresponding questions are related to a laser bond DPM technique. 14.The parts marking system of claim 13, wherein the logic is furtherconfigured to determine, based upon one or more inputs in response tothe questions, whether the laser bond DPM technique is possible.
 15. Aparts marking method for determining a type of direct parts marking(DPM) to be used for a particular part, comprising: storing dataindicative of a plurality of materials out of which the part can be madeand storing in memory for each material a plurality DPM techniques and aplurality of technical limitations associated with the DPM technique,the technical limitations including data for determining whether eachDPM technique can be used based upon each material; receiving data, viaa graphical user interface (GUI), identifying a part and a material outof which the part is made; displaying, based upon the data identifyingthe part and the material out of which the part is made via the GUI,data identifying at least one of the DPM techniques and the technicallimitations associated with the DPM technique, each limitation displayedin the form of a question.
 16. The parts marking method of claim 15,further comprising displaying one or more general technical limitationsrelating to DPM techniques in the form of questions.
 17. The partsmarking method of claim 16, determining, based upon one or more inputsin response to the questions corresponding to the one or more generaltechnical limitations, that DPM is not possible for the identified partand characteristics of the material.
 18. The parts marking method ofclaim 16, further comprising determining, based upon one or more inputsin response to the questions corresponding to the one or more generaltechnical limitations, that DPM is possible for the identified part andthe identified material.
 19. The parts marking method of claim 15,further comprising displaying one or more specific technical limitationsrelating to a particular DPM technique in the form of questions.
 20. Theparts marking method of claim 19, wherein the logic is furtherconfigured to determine, based upon one or more inputs in response tothe questions, whether the particular DPM technique is possible for theidentified part and the identified material.
 21. The parts markingmethod of claim 19, wherein the specific technical limitations and thecorresponding questions are related to a dot peen DPM technique.
 22. Theparts marking method of claim 21, further comprising determining, basedupon one or more inputs in response to the questions, whether the dotpeen DPM technique is possible.
 23. The parts marking method of claim19, wherein the specific technical limitations and the correspondingquestions are related to an ink jet DPM technique.
 24. The parts markingmethod of claim 23, further comprising determining, based upon one ormore inputs in response to the questions, whether the ink jet DPMtechnique is possible.
 25. The parts marking method of claim 19, whereinthe specific technical limitations and the corresponding questions arerelated to a chemical etch DPM technique.
 26. The parts marking methodof claim 25, further comprising determining, based upon one or moreinputs in response to the questions, whether the chemical etch DPMtechnique is possible.
 27. The parts marking method of claim 19, whereinthe specific technical limitations and the corresponding questions arerelated to a laser bond DPM technique.
 28. The parts marking method ofclaim 27, further comprising determining, based upon one or more inputsin response to the questions, whether the laser bond DPM technique ispossible.
 29. The parts marking method of claim 19, further comprisingdisplaying a list of possible DPM techniques based upon the identifiedpart and identified material.